A simple wildcard syntax can be used with the component
name to allow a single rule to apply to multiple SGs as follows:
abc - Exactly these characters
? Any one character
* Any zero or more characters
+ Zero or more additional occurrences of the previous
match
[a-z0-9] Any of these characters
[!a-z] Anything but one of these
characters
All SG name comparisons are case-insensitive. The
following examples show how they are interpreted:
Table 1. Wildcard
syntax examples
| This pattern |
Matches these Storage
Groups |
Does not match these
Storage Groups |
| tg_* |
tg_DB_SG1 or tg_newSG
or TG_sg_db |
tgNewSG |
| prod_sg? |
prod_sg1 or prod_sga
por Prod_sg2 |
prod_sg12 or
prod_sgab |
| prod_sg[0-9]+ |
prod_sg1 or prod_sg12 |
prod_sga or prod_sgab
|
The only allowed characters are: a-zA-Z0-9_- along with
the above *+?[]! wildcard characters.
The only roles that can be assigned against storage
groups are: Local Replication, Remote Replication, and Device
Management.
Storage groups do not have to exist at the time that a
matching Role-Based Authentication Controls (RBAC) rule for them is
defined.
These storage groups-level RBAC rules are only applicable
to parent and stand-alone SGs and not child SGs. Child SGs are
protected by the RBAC rules, if any, on their parent SG.